explorer.exe windows error the instruction at 0x65a7f4bb refernced memory at 0x000000000 the memory could not be read
i want help me for this problem
windows 10 build 10130 explorer.exe windows error
June 7th, 2015 11:39am
this window com to me when i shutdown or restart the computer
Free Windows Admin Tool Kit Click here and download it now
June 7th, 2015 11:40am
Hi,
The most common cause of this error is a background application interference.
Please terminate all background applications to check the result.
Besides that, also please try these methods:
1. Run sfc /scannow command to fix the corrupted or missing system file.
2. Increase virtual memory.
3. Update all drivers
More information, please refer to this guide:
http://helpdeskgeek.com/help-desk/instruction-at-referenced-memory-could-not-be-read/
Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
June 9th, 2015 5:39am
After an automatic upgrade to build 10130 of Win 10 (I'm on the slow ring), and a subsequent installation of Visual Studio Professional 2015 RC, I have the same access violation error. I also observed that the Nvidia drivers were updated by either the Win10 update or VS installation, but they weren't recognized by the system, so I downloaded a slightly newer version directly from Nvidia and performed a clean installation on the display drivers. However, I continued to have problems launching applications that worked prior to this problem. One application complained that VCOMP110.DLL was missing from the system
I ran the sfc /scannow which gave this output:
Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in offline servicing scenarios.
The log file indicated one corrupt file which may need to be fixed:
2015-06-16 09:43:29, Info CSI 00008cf4 [SR] Beginning Verify and Repair transaction
2015-06-16 09:43:29, Info CSI 00008cf5 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10130.0_none_364434c361d4c5ff\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
Found: {l:32 b:7SKvutPJrG+HEGkivYNnXHYEsZLLUmFEvWIH2J6p834=} Expected: {l:32 b:Dqceoy/mIKXOlF+7fdx+vIUDURWwLzgdrVoxH1yiA6A=}
2015-06-16 09:43:29, Info CSI 00008cf6 [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10130.0, pA Host= PROCESSOR_ARCHITECTURE_AMD64 (9) Guest= PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral in the store, hash mismatch
2015-06-16 09:43:29, Info CSI 00008cf7 Total number of unique security descriptors: 0
2015-06-16 09:43:29, Info CSI 00008cf8@2015/6/16:13:43:29.385 Primitive installers committed for repair
2015-06-16 09:43:29, Info CSI 00008cf9 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10130.0_none_364434c361d4c5ff\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
Found: {l:32 b:7SKvutPJrG+HEGkivYNnXHYEsZLLUmFEvWIH2J6p834=} Expected: {l:32 b:Dqceoy/mIKXOlF+7fdx+vIUDURWwLzgdrVoxH1yiA6A=}
2015-06-16 09:43:29, Info CSI 00008cfa [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10130.0, pA Host= PROCESSOR_ARCHITECTURE_AMD64 (9) Guest= PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral in the store, hash mismatch
2015-06-16 09:43:29, Info CSI 00008cfb [SR] This component was referenced by [l:250{125}]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10130.0.RemoteFX clientVM and UMTS files and regkeys"
2015-06-16 09:43:29, Info CSI 00008cfc Hashes for file member \??\C:\WINDOWS\SysWOW64\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
Found: {l:32 b:GMWyoWJq+uQPLJTX+8rNbrf3eTYEbPcBUEoc5krMpBw=} Expected: {l:32 b:Dqceoy/mIKXOlF+7fdx+vIUDURWwLzgdrVoxH1yiA6A=}
2015-06-16 09:43:29, Info CSI 00008cfd Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10130.0_none_364434c361d4c5ff\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
Found: {l:32 b:7SKvutPJrG+HEGkivYNnXHYEsZLLUmFEvWIH2J6p834=} Expected: {l:32 b:Dqceoy/mIKXOlF+7fdx+vIUDURWwLzgdrVoxH1yiA6A=}
2015-06-16 09:43:29, Info CSI 00008cfe [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\WINDOWS\SysWOW64"\[l:20{10}]"opencl.dll"; source file in store is also corrupted
2015-06-16 09:43:29, Info CSI 00008cff Total number of unique security descriptors: 0
2015-06-16 09:43:29, Info CSI 00008d00@2015/6/16:13:43:29.416 Primitive installers committed for repair
2015-06-16 09:43:29, Info CSI 00008d01 [SR] Repair complete
2015-06-16 09:43:29, Info CSI 00008d02 [SR] Committing transaction
2015-06-16 09:43:29, Info CSI 00008d03 Creating NT transaction (seq 2), objectname [6]"(null)"
2015-06-16 09:43:29, Info CSI 00008d04 Created NT transaction (seq 2) result 0x00000000, handle @0x3cc
2015-06-16 09:43:29, Info CSI 00008d05@2015/6/16:13:43:29.572 Beginning NT transaction commit...
2015-06-16 09:43:29, Info CSI 00008d06@2015/6/16:13:43:29.604 CSI perf trace:
CSIPERF:TXCOMMIT;42937
2015-06-16 09:43:29, Info CSI 00008d07 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
Can you tell me how to proceed with this output from sfc? Thanks.
- Edited by ADSK-Himanshu Tuesday, June 16, 2015 1:57 PM
Free Windows Admin Tool Kit Click here and download it now
June 16th, 2015 1:54pm
After an automatic upgrade to build 10130 of Win 10 (I'm on the slow ring), and a subsequent installation of Visual Studio Professional 2015 RC, I have the same access violation error. I also observed that the Nvidia drivers were updated by either the Win10 update or VS installation, but they weren't recognized by the system, so I downloaded a slightly newer version directly from Nvidia and performed a clean installation on the display drivers. However, I continued to have problems launching applications that worked prior to this problem. One application complained that VCOMP110.DLL was missing from the system
I ran the sfc /scannow which gave this output:
Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in offline servicing scenarios.
The log file indicated one corrupt file which may need to be fixed:
2015-06-16 09:43:29, Info CSI 00008cf4 [SR] Beginning Verify and Repair transaction
2015-06-16 09:43:29, Info CSI 00008cf5 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10130.0_none_364434c361d4c5ff\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
Found: {l:32 b:7SKvutPJrG+HEGkivYNnXHYEsZLLUmFEvWIH2J6p834=} Expected: {l:32 b:Dqceoy/mIKXOlF+7fdx+vIUDURWwLzgdrVoxH1yiA6A=}
2015-06-16 09:43:29, Info CSI 00008cf6 [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10130.0, pA Host= PROCESSOR_ARCHITECTURE_AMD64 (9) Guest= PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral in the store, hash mismatch
2015-06-16 09:43:29, Info CSI 00008cf7 Total number of unique security descriptors: 0
2015-06-16 09:43:29, Info CSI 00008cf8@2015/6/16:13:43:29.385 Primitive installers committed for repair
2015-06-16 09:43:29, Info CSI 00008cf9 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10130.0_none_364434c361d4c5ff\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
Found: {l:32 b:7SKvutPJrG+HEGkivYNnXHYEsZLLUmFEvWIH2J6p834=} Expected: {l:32 b:Dqceoy/mIKXOlF+7fdx+vIUDURWwLzgdrVoxH1yiA6A=}
2015-06-16 09:43:29, Info CSI 00008cfa [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10130.0, pA Host= PROCESSOR_ARCHITECTURE_AMD64 (9) Guest= PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral in the store, hash mismatch
2015-06-16 09:43:29, Info CSI 00008cfb [SR] This component was referenced by [l:250{125}]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10130.0.RemoteFX clientVM and UMTS files and regkeys"
2015-06-16 09:43:29, Info CSI 00008cfc Hashes for file member \??\C:\WINDOWS\SysWOW64\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
Found: {l:32 b:GMWyoWJq+uQPLJTX+8rNbrf3eTYEbPcBUEoc5krMpBw=} Expected: {l:32 b:Dqceoy/mIKXOlF+7fdx+vIUDURWwLzgdrVoxH1yiA6A=}
2015-06-16 09:43:29, Info CSI 00008cfd Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10130.0_none_364434c361d4c5ff\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
Found: {l:32 b:7SKvutPJrG+HEGkivYNnXHYEsZLLUmFEvWIH2J6p834=} Expected: {l:32 b:Dqceoy/mIKXOlF+7fdx+vIUDURWwLzgdrVoxH1yiA6A=}
2015-06-16 09:43:29, Info CSI 00008cfe [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\WINDOWS\SysWOW64"\[l:20{10}]"opencl.dll"; source file in store is also corrupted
2015-06-16 09:43:29, Info CSI 00008cff Total number of unique security descriptors: 0
2015-06-16 09:43:29, Info CSI 00008d00@2015/6/16:13:43:29.416 Primitive installers committed for repair
2015-06-16 09:43:29, Info CSI 00008d01 [SR] Repair complete
2015-06-16 09:43:29, Info CSI 00008d02 [SR] Committing transaction
2015-06-16 09:43:29, Info CSI 00008d03 Creating NT transaction (seq 2), objectname [6]"(null)"
2015-06-16 09:43:29, Info CSI 00008d04 Created NT transaction (seq 2) result 0x00000000, handle @0x3cc
2015-06-16 09:43:29, Info CSI 00008d05@2015/6/16:13:43:29.572 Beginning NT transaction commit...
2015-06-16 09:43:29, Info CSI 00008d06@2015/6/16:13:43:29.604 CSI perf trace:
CSIPERF:TXCOMMIT;42937
2015-06-16 09:43:29, Info CSI 00008d07 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
Can you tell me how to proceed with this output from sfc? Thanks.
- Edited by ADSK-Himanshu Tuesday, June 16, 2015 1:57 PM
June 16th, 2015 1:54pm
After an automatic upgrade to build 10130 of Win 10 (I'm on the slow ring), and a subsequent installation of Visual Studio Professional 2015 RC, I have the same access violation error. I also observed that the Nvidia drivers were updated by either the Win10 update or VS installation, but they weren't recognized by the system, so I downloaded a slightly newer version directly from Nvidia and performed a clean installation on the display drivers. However, I continued to have problems launching applications that worked prior to this problem. One application complained that VCOMP110.DLL was missing from the system
I ran the sfc /scannow which gave this output:
Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in offline servicing scenarios.
The log file indicated one corrupt file which may need to be fixed:
2015-06-16 09:43:29, Info CSI 00008cf4 [SR] Beginning Verify and Repair transaction
2015-06-16 09:43:29, Info CSI 00008cf5 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10130.0_none_364434c361d4c5ff\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
Found: {l:32 b:7SKvutPJrG+HEGkivYNnXHYEsZLLUmFEvWIH2J6p834=} Expected: {l:32 b:Dqceoy/mIKXOlF+7fdx+vIUDURWwLzgdrVoxH1yiA6A=}
2015-06-16 09:43:29, Info CSI 00008cf6 [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10130.0, pA Host= PROCESSOR_ARCHITECTURE_AMD64 (9) Guest= PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral in the store, hash mismatch
2015-06-16 09:43:29, Info CSI 00008cf7 Total number of unique security descriptors: 0
2015-06-16 09:43:29, Info CSI 00008cf8@2015/6/16:13:43:29.385 Primitive installers committed for repair
2015-06-16 09:43:29, Info CSI 00008cf9 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10130.0_none_364434c361d4c5ff\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
Found: {l:32 b:7SKvutPJrG+HEGkivYNnXHYEsZLLUmFEvWIH2J6p834=} Expected: {l:32 b:Dqceoy/mIKXOlF+7fdx+vIUDURWwLzgdrVoxH1yiA6A=}
2015-06-16 09:43:29, Info CSI 00008cfa [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10130.0, pA Host= PROCESSOR_ARCHITECTURE_AMD64 (9) Guest= PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral in the store, hash mismatch
2015-06-16 09:43:29, Info CSI 00008cfb [SR] This component was referenced by [l:250{125}]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10130.0.RemoteFX clientVM and UMTS files and regkeys"
2015-06-16 09:43:29, Info CSI 00008cfc Hashes for file member \??\C:\WINDOWS\SysWOW64\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
Found: {l:32 b:GMWyoWJq+uQPLJTX+8rNbrf3eTYEbPcBUEoc5krMpBw=} Expected: {l:32 b:Dqceoy/mIKXOlF+7fdx+vIUDURWwLzgdrVoxH1yiA6A=}
2015-06-16 09:43:29, Info CSI 00008cfd Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10130.0_none_364434c361d4c5ff\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
Found: {l:32 b:7SKvutPJrG+HEGkivYNnXHYEsZLLUmFEvWIH2J6p834=} Expected: {l:32 b:Dqceoy/mIKXOlF+7fdx+vIUDURWwLzgdrVoxH1yiA6A=}
2015-06-16 09:43:29, Info CSI 00008cfe [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\WINDOWS\SysWOW64"\[l:20{10}]"opencl.dll"; source file in store is also corrupted
2015-06-16 09:43:29, Info CSI 00008cff Total number of unique security descriptors: 0
2015-06-16 09:43:29, Info CSI 00008d00@2015/6/16:13:43:29.416 Primitive installers committed for repair
2015-06-16 09:43:29, Info CSI 00008d01 [SR] Repair complete
2015-06-16 09:43:29, Info CSI 00008d02 [SR] Committing transaction
2015-06-16 09:43:29, Info CSI 00008d03 Creating NT transaction (seq 2), objectname [6]"(null)"
2015-06-16 09:43:29, Info CSI 00008d04 Created NT transaction (seq 2) result 0x00000000, handle @0x3cc
2015-06-16 09:43:29, Info CSI 00008d05@2015/6/16:13:43:29.572 Beginning NT transaction commit...
2015-06-16 09:43:29, Info CSI 00008d06@2015/6/16:13:43:29.604 CSI perf trace:
CSIPERF:TXCOMMIT;42937
2015-06-16 09:43:29, Info CSI 00008d07 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
Can you tell me how to proceed with this output from sfc? Thanks.
- Edited by ADSK-Himanshu 17 hours 16 minutes ago
Free Windows Admin Tool Kit Click here and download it now
June 17th, 2015 10:08am
To resolve my problems, I had to:
- Perform a clean install the graphics card drivers for Nvidia Quadro FX 1800
- Repair the installation of Visual C++ Redistributable
Now my systems *seems* to be OK.
June 19th, 2015 3:14pm
This topic is archived. No further replies will be accepted.
Other recent topics
